Security rating method

ABSTRACT

Security rating method and a graphical tool for decision making especially for setting priorities which tool comprises at least one diagram ( 1 ) having a first scale ( 2 ) which reaches in a first direction along a first axis ( 3 ), at least a first ( 4 ) and a second ( 5 ) potential action fields the identified value of which ( 4   a,    4   b ) is graphically represented on said first scale ( 2 ) in said diagram ( 1 ) whereby a second scale ( 6 ) is arranged along said first axis. Said second scale ( 6 ) reaches in an opposite direction to said first scale.

TECHNICAL FIELD

[0001] Traditionally, when mentioning computer security, IT-security has been the most commonly used concept. When we say IT-security we usually mean technical aspects of computer security. Up to this date it is traditionally where most of the work has been concentrated the past few years.

[0002] By stating the notion Information Security we actually mean a larger part of the computer security. Information Security does not only cover the technical aspects, but also the administrative and physical aspects. The administrative aspects cover the routines and documentation while the physical aspects cover the buildings and storage of the computers and their information. The Information Security notion cover more areas and more than just the technical aspects.

[0003] Everybody knows what good Information Security level is, or at least we have an idea about what the market says is a good level. The level of Information Security that we adopt today is usually based on what we have to protect. If we have a lot of classified information, we have demands of a high Information Security level. If our information is open to everybody, we are usually satisfied with a lower level. But how can we know which level that is appropriate?

[0004] What is needed, is a way to express this level of Information Security and invent a new way of factors and definitions, a “common language”. A company A which is going to connect their network to company B needs a way to know that their Information Security level is similar, or at least similar in some specific areas. We need a way to measure the Information Security level at companies A and B, and a method to compare the levels. Company A and B may be operating under different regulations or different legislation, depending on their branch of trade. We also need a method to cover this situation. Companies A and B will be able to use the method according to the invention to communicate their needs between each other.

[0005] But how can Information Security levels be measured? To measure using statistics is one way by sampling values and construct definitions. This is difficult because there is nothing to compare against. The other way to measure is using a relative method. We can say that one protection or implementation is better than another. To use a relative method to measure Information Security forms the basis of the method for rating according to the present invention.

BRIEF DESCRIPTION OF THE INVENTION

[0006] The relative method according to the invention is based on performing measurements on specific Information Security issues within an organisation. These issues are called checkpoints. All checkpoints are divided into three information security areas: logical, physical and system security. A fourth area could be added, cf. below. Logical security cover administrative aspects like polices and guidelines with a perspective on the personnel. Physical security cover all the facilities while system security cover the IT-systems themselves.

[0007] The method according to the invention states a norm level for Information Security which is based on the current market situation. This norm is formed by current standards and recommendations for Information Security. The various information sources which are used to construct the norm level within the method is together called the information set. All demands and appliances are derived from the information set to form the norm level.

[0008] From the norm level, four other levels are created in the described example. This is made to meet the need for different types of information security levels and requirements. Two lower levels are created from the norm which g nerally have a smaller amount of checkpoints and the demands are less strict. Above the norm two higher levels are created which generally have a larger amounts of checkpoints and the demands are stricter. Measurements can be performed towards each level by doing analysis and inspections on the three information security areas.

[0009] During the analysis and inspections each checkpoint is given a grade. The grade is given on scale which generally indicate the fulfilment towards the demand on the specific checkpoint. When each checkpoint has been given a grade several results are calculated. The mathematical operations to calculate the results consider several organisation properties. To consider the properties when calculating the results within the method is vital to be able to use the results between organisations. The consideration to properties ensure that each result is comparable between organisations.

[0010] If the results indicate that the organisation has passed the analysis, a certification organisation has the right to issue a certificate. The certificate will state which level that is passed and the results in each area.

[0011] The described method will be developped into new versions to meet the ever changing needs and demands within the information security area. A new version will change demands, add checkpoints and reconstruct the analysis. When to issue a new version is governed by the availability of new sources if information like new legislation, new security techniques, a change of social behaviours etc.

[0012] The analysis according to the method is supported by a software tool. This tool can also perform all the result calculations and present the results. Organisations may use the tool to perform the analysis themselves, but in that case the result calculations are locked out. This is because the method must be controlled by one party to insure that results are coherent and thus possible to compare.

DETAILED DESCRIPTION OF THE INVENTION

[0013] The rating method according to the invention will now be described more in detail. First certain definitions and abbreviations will be elucidated. Then follows a part describing the results obtained by means of the method according to the invention.

[0014] Definition of Roles

[0015] A certain terminology is used in the description of the method, e.g. for defining organisation specific parts and their context. There are also definitions used for the organisation performing the measurement. Entity The actual organisation that is subjected to the information security measurement Entity Owner This is the overall responsible function for Information security at the Entity or within a group of entities that shares information Rating The Independent organisation that conducts the rating Reviewer measurement process. This is also the license company that gets the license to use the method, license taker. (ref. To as Reviewer) Reviewer The Independent organisation team which always team should at least consist of three persons. Each person should have his or her major knowledge within some of the three information security areas. License provides the license and also has the basis for determine Provider the final results (result method part). Client The person/function at the Entity owner that has ordered the rating.

[0016] Method Areas—Definition of Information Security

[0017] Within the method, three areas are defined on which to perform the measurements. These areas are: Logical Administrative information security like policies, guidelines etc. Security Logical security focuses on personnel and documentation within the organisation measured. Physical Information security regarding facilities, fire and burglar Security protection etc. Physical security focuses on the personnel as well as the facilities within the organisation measured. System Information security regarding network, operating systems and Security applications. System security focuses on personnel, and the level of IT-systems' technical security within the organisation measured.

[0018] Definition of Measurement Levels

[0019] The basis and uniqueness for the method are the pre-set levels of information security. The levels are derived form a predefined scale and a norm set as level 3. A higher number on the scale equals a larger set of information security analysis. A higher number on the scale also represents a higher set of demands to be fulfilled. Present levels of the concept using the method are: Veriscan 1 Controlled Information Security Veriscan 2 Information Security Aware Veriscan 3 Market adapted Information Security (current market norm) Veriscan 4 High Information Security Veriscan 5 Very High Information Security

[0020] Demands are relatively set from a standard level (norm). The middle level within the total number of levels represents the norm. From the norm level, lower levels and higher levels are set. In the five levels shown above in this example, the norm is based at level 3 (Veriscan 3). The norm is derived from demands set by dependant and independent organisations through standards, guidelines and policies. Other market demands within the information security area also have impact on the construction of the norm level. The middle level will always be named “Market adopted Information Security” to reflect the level of demands that are put onto organisations, both in amount of demands and the level of demand fulfilment.

[0021] The statement above provides that the levels described always must be developed to meet the market demands within the Information Security Area. This also means that each level must have it's own version number of method used. The version number describes future developments of the method.

[0022] Definition of Information Set

[0023] In order to set and develop the different levels information is gathered from various sources. In this example the following is a list of such sources:

[0024] National and international standards, such as BS7799, SS627799, ISO17799 etc.

[0025] Military standards, such as FA22 and various DoD standards

[0026] Internet Standards—RFC's

[0027] Legislation, national and international

[0028] Company specific standards or guidelines

[0029] National and international standardisation committees

[0030] Various information security methods and guidelines

[0031] Various information security literature

[0032] Physical security standards and recommendations

[0033] Several of the information sources mentioned above contain information that is similar or identical to information from other sources on the list. Several books include the topics covered within standard from another point of view. Information about information security within literature has more often a more aggressive approach towards problems covered. This approach is used within the method to further develop the various version numbers of a level.

[0034] Definition of Method Terminology

[0035] Each information security area (Logical, Physical and System) is divided into measurement categories. The categories reflect certain sub areas within an information security area. A category is further divided into checkpoints. The checkpoints are the actual measurements performed by analysis, interviews, inspection or tests etc. The definitions are stated as follows: Level The actual rating level measured, e.g. Veriscan 1 to 5 Area The three Information security areas; Logical, Physical and System Category A service or specific part in the organisation Information security Checkpoint A specific function within a category

[0036] The connections between these definitions can also be viewed in FIG. 2.a.

[0037] Definition of Method Weights

[0038] The method consists of weights used during calculations of the results in the method result part. The weights are used within the method to solve the following problems:

[0039] Which type of entity is measured?

[0040] Who is the person respondent answering questions during interviews (his or hers responsibility)?

[0041] How many of the entity personnel are going to be interviewed?

[0042] Who is the person from the license provider doing the actual measurement?

[0043] What is the current level of threats against the measured entity?

[0044] What is the consequence on a specific resource?

[0045] What is the probability that some thing happens on some information resource?

[0046] Is a checkpoint generally more important than another one?

[0047] Is a category generally more important than another one?

[0048] What are the general efforts that the entity has to mobilise to solve an information security problem?

[0049] Each weight is explained in the following.

[0050] Threat Weight:

[0051] The threat weight represents a general level of threat against the checkpoint measured within a scale from 1 to 5. A higher threat weight represents a high threat and a lower weight represent a low threat. The actual threat weight on a specific checkpoint is deduced from a generalisation performed by the license provider.

[0052] Probability Weight:

[0053] The probability weight represents a general level of probability that a certain action will be fulfilled if the threat on the checkpoint is activated on a scale of 1 to 5. A lower weight represents a low probability and high weight represents a high probability. The actual probability weight on a specific checkpoint is deduced from a generalisation performed by the license provider.

[0054] Consequence Weight:

[0055] The consequence weight represents a general level of consequence for the entity measured if both the threat and probability of checkpoint has activated on a scale of 1 to 5. A lower weight represents a low consequence and high weight represents a high consequence. The actual consequence weight on a specific checkpoint is deduced from a generalisation performed by the license provider.

[0056] Checkpoint Weight:

[0057] By adding the threat, probability and consequence weights to each other and divide with the numbers of factors used, a factor called the checkpoint weight is created. The checkpoint weight represents the importance of the checkpoint towards other checkpoints.

[0058] Category Weight:

[0059] A set of checkpoints form a category. The category weight is like the checkpoint weight built on three factors: threat, probability and consequence. There is a major difference between the checkpoint weight and the category weight in the manner that the actual category weight can be derived from two different aspects. The first type of category weight is derived from a generalisation on the three factors threat, probability and consequence. This generalisation is performed during measurement setup in discussions with the entity owner.

[0060] The other type of category weight is derived from a mean value from all the checkpoints threat, probability and consequence factors.

[0061] Which approach that is used is decided upon measurement setup between the license provider and the entity owner. Within the method these two approaches on category weight are called pre-set category weight and derived category weight.

[0062] Position Weight:

[0063] Upon measurement interviews will be performed with people who have different types of responsibility. To limit variations, that may be due to the fact that the actual sample do not reflect the organisation structure of the Entity, the Position Weight is used. Like in the previous weights a 5-graded scale is used, where 1 represents a low position weight and 5 represent a high position weight. All position weights are explained below:

[0064] 1. A person with no responsibility for information security issues. This person does not participate in any issues regarding information security. Typically ordinary users of IT systems will constitute this.

[0065] 2. A person with minor responsibilities within information security areas. This person may participate in some kind of forum regarding information security issues. Typically persons that have some kind of responsibility regarding IT systems, facilities or organisation structure will get this position weight.

[0066] 3. Person responsibilities within information security areas. This person have this responsibility as his or hers daily routine. Persons, which get this position weight often, have their responsibilltes towards an IT function within the entity. All personnel from the measuring organisation will have a position weight of 3.

[0067] 4. A person, which have major responsibilities within information security areas. Persons, which get this weight, may be on executive level within the entity, or they may have some overall responsibility for IT function or specific information security areas or issues.

[0068] 5. A person, which have the highest responsibility for issues regarding information security. Typically this person is on executive level.

[0069] The position weight is used in the method to grade answers, inspection or analysis. It's vital that all the position weights together don't give a false or weighted result. For example, a person having a high position weight will have higher impact on the checkpoint result than a person with a low position weight.

[0070] The license provider adds a restriction on position weights of the entity saying: There must always be enough lower position weights to cover a higher position weight. For example this means that if there is one person participating who has a position weight of 4, there must be at least 4 people with position weight of 1 to cover.

[0071] The example described above gives the notion that this may not always be true. There may not be enough persons to cover a higher position weight. Therefore, the method uses fictitious persons to cover. These fictitious persons are based on a mean value of the results from the other persons within the same position weight.

[0072] Time Effort Weight:

[0073] Each checkpoint has some drawback if the measurement gives a result that is below the norm, 3. To be able to measure the effort in time that the entity has to provide to correct (i.e. pass) the checkpoint from a very low state, the time effort weight is introduced into the method. The time effort weight uses a scale form 0 to 5 where a low time effort weight represent that the entity has to put aside a minimum of time to solve the problem. A high time effort weight represent that the entity has to put aside a considerably amount of time to solve the problem. The complete scale of time effort weight is presented below.

[0074] 0. No time must be put aside to solve the problem. This is actually a special case and will not be used often because to correct a potential problem the entity must put time aside.

[0075] 1. A small amount of time must be put aside to solve the problem. Typically a time effort weight of 1 represents a work time amount of minutes. Usually the effort can be solved within the entity.

[0076] 2. A minor amount of time must be put aside to solve the problem. Typically a time effort weight of 2 represents a work time amount of hours. Usually the effort can be solved within the entity.

[0077] 3. A medium about of time must be put aside to solve the problem. Typically a time effort weight of 3 represents a work time amount of days up to one week. Usually the effort can be solved within the entity. Additional help from outside the entity may be required.

[0078] 4. A considerable about of time must be put aside to solve the problem. Typically a time effort weight of 4 represents a work time amount of weeks or up to one month. Usually the effort cannot be solved within the entity. Additional help from outside the entity is required.

[0079] 5. A substantial about of time must be put aside to solve the problem. Typically a time effort weight of 5 represents a work time amount of months or years. Additional help from outside the entity is always required.

[0080] Cost Effort Weight:

[0081] To be able to measure the effort in costs that the entity has to provide to correct (i.e. pass) the checkpoint from a very low state, the cost effort weight is introduced into the method. The cost effort weight uses a scale form 0 to 5 where a low cost effort weight represent that the entity has to put aside a minimum of funds to solve the problem. A high cost effort weight represent that the entity has to put aside a considerably amount of funds to solve the problem. The complete scale of time effort weight is presented below.

[0082] 0. No amount of funds must be put aside to solve the problem.

[0083] 1. A small amount of funds must be put aside to solve the problem. Typically a cost effort weight of 1 represents funds below $100.

[0084] 2. A minor amount of funds must be put aside to solve the problem. Typically a cost effort weight of 2 represents funds below $1000.

[0085] 3. A medium about of funds must be put aside to solve the problem. Typically a cost effort weight of 3 represent funds below $10000

[0086] 4. A considerable about of funds must be put aside to solve the problem. Typically a cost effort weight of 4 represents funds below $100000.

[0087] 5. A substantial about of funds must be put aside to solve the problem. Typically a cost effort weight of 5 represent funds over $100000.

[0088] Effort Weight:

[0089] The time effort weight and the cost effort weight form the actual effort weight for a particular checkpoint. This is done by adding the participating types of effort weights to each other and then by dividing with the number of effort weights. By stating this last condition the effort weight may include further effort factors in later versions.

[0090] Entity Template:

[0091] Together the effort weight, threat, probability and consequence form several factors between 1 to 5 for each measured checkpoint. All the factors for each checkpoint form a matrix called the entity template. The entity template forms the basics for importance and the different effort between checkpoints.

[0092] The license provider form the basic entity template for each measured level. Upon measurement setup the entity owner has the right to adjust the basic entity template to meet the measured entity's needs or structure. The license provider has set a constriction on modifications on the template, which include that no factor may increase more than one and no factor may decrease more than one.

[0093] If an entity will choose to alter the basic entity template, the altered version will be used in all the sub entities within the measured organisation.

[0094] The license provider also has the possibility to alter the entity template to meet certain conditions stated for different types of entities. There may be an entity template for health care and another for process industry, for example.

[0095] In order to have an open comparison independent of variations of the actual entity should generally an altered entity template not be considered and the basic entity template should be used.

[0096] Definition of Checkpoint Grades

[0097] Each checkpoint that is measured is given a grade. The grade is set upon a specific checkpoint during interviews, inspections, system analysis or documentation analysis. The grade is constructed with a six graded scale, where 0 is the lowest grade and 5 the highest. Like in the method level norm, a norm grade is used on a specific checkpoint. This norm is also set to 3. A grade lower than 3 represent a checkpoint that is not passed, and likewise a grade higher than or equal to 3 represent a passed checkpoint. All present checkpoint grades and their meaning are stated below. The meaning of the actual grade is different depending upon the information security area measured. Grade0 There are severe/crucial shortages or lack of information (Failed) resources concerning: Knowledge Documents or document content System implementations or configurations Facilities, facility construction or Implementations Grade 1 There are major shortages of Information resources (Failed) concerning: Knowledge Documents or document content System Implementations or configurations Facilities, facility construction or Implementations Grade 2 There are minor shortages of Information resources (Failed) concerning: Knowledge Documents or document content System Implementations or configurations Facilities, facility construction or Implementations Grade 3 There are no shortages of Information resources concerning: (Passed) Knowledge Documents or document content System Implementations or configurations Facilities, facility construction or Implementations Grade 4 There are no shortages of Information resources concerning: (Passed) (and checkpoints passed with commendation): Knowledge Documents or document content System implementations or configurations Facilities, facility construction or Implementations Grade 5 There are no shortages of Information resources concerning (Passed) (and checkpoints passed with high commendation): Knowledge Documents or document content System implementations or configurations Facilities, facility construction or implementations

[0098] The grades can also be seen as an analogue scale using natural numbers adapted to each information security area as follows:

[0099] The definitions on how each grade is set upon a specific checkpoint will be discussed later in this document.

[0100] Definition of Checkpoint Demands

[0101] The approach of grading is achieved by stating a specific demand on each checkpoint. The demand may vary from a specific text that must exist within the controlled entity's security policy or that a specific type of door must be used in the computer room. Within the system security area for example, must the e-mail service be configured in a way that will minimise a security breach. All these conditions form together the method demands. As stated earlier the demands will vary from each information security level. All checkpoint demands are derived from the information set.

[0102] Definition of Result Grades 1 to 5

[0103] If the demand on a specific checkpoint is fulfilled, a checkpoint grade of at least 3 will be given. To give a checkpoint a grade of 3 is actually not a major problem because the demand is derived from the information set, which it's based upon standards like BS7799, SS3492 etc. To give a grade of 0 is not either a difficult task, because this grade states a total lack of information or protection. The tricky part is to grade a checkpoint either lower (1 or 2) or higher (4 or 5) than 3.

[0104] This latter part is up to the rating reviewer. It's his or hers responsibility to give a correct grade on the checkpoint. The actual grade properties have been stated earlier and those statements form the basics within the method to give a correct grade. To pass a certain checkpoint the demands must be completely fulfilled. On each demand there is also a negative and a positive aspect defined and described. These aspects will act as a grading guide on each checkpoint and help the reviewer towards giving a correct grade during the analysis.

[0105] The positive and negative aspects are stated in a generalised form. For example a checkpoint about fire protection in the computer room will at rating level of 3 have the demand stating that a fire extinguisher of the proper type should be placed easily accessible and signs have to be in place. A typical positive aspect on this checkpoint will be if the extinguisher is placed in an excellent position, it has been controlled recently and there are signs which are both obvious and of a excellent quality. A typical negative aspect will be if the extinguisher is not of the proper type (extinguish electrical fires), it's not obvious where to find it and signs may be misplaced. The amount of positive and negative aspects on a specific checkpoint will guide the reviewer to the correct grade.

[0106] But there is a potential risk that one checkpoint may be given different grades depending on who the rating reviewer is.

[0107] To meet this potential risk the method states that each checkpoint, where there are doubts must be controlled within the rating reviewed team. The method states that all checkpoints, even if there is only the slightest of doubts upon the grade, should always be reviewed by the rating reviewers team. It's then up to the team to set the final grade. By adopting this technique within the method, there is only a minor chance of faulty grades.

[0108] When all grades have been set for all three information security areas, the basis for calculating the final results are in place.

[0109] Method Development and Versions

[0110] Norm Level Development

[0111] To put all the demands and set of fulfillments into the method, the license provider determines the set of criteria forming the norm. This is done by analysis of the various sources mentioned in the previous chapter 2.2. All the analysis is performed by identifying the common parts between each information resource. The common parts are stated as the backbone for the norm level, Veriscan 3. This is done on each information security area: Logical, Physical and System.

[0112] The backbone information resource is evaluated against current market information security demands, fulfillments and actual market situation. The information set produced after evaluation form the full set of information used in the norm level, Veriscan 3.

[0113] On the full set of information the license provider, performs various tasks to group, divide and adopt the information set into the method. This step creates the areas, categories and checkpoints of the norm as described in chapter 2.2.

[0114] As time goes by new features and factors will change the global information security market. New technologies will be adopted and many security issues will be both changed and revised. For example, there will be new inventions to meet threats from hackers and crackers and the method must have a built in support to deal with these kind of situations. This means that the checkpoints, weights, demands and so on will have to change over time.

[0115] To meet the ever changing information security market the method uses a version numbering. The method version numbering uses three number stated as a.b.c. The a represents a major version/revision, the b represent the market version and the c stands for the internal working revision number. Analysis towards an entity can only be performed on a market version.

[0116] The method states that a new major version can only be released if all information security areas are revised onto the corresponding major version, i.e. 1.b, 2.b, 3.b etc. This means if some area is to be revised onto a new major version the other areas must also be revised.

[0117] The market versions are the actual versions which are used to perform analysis and measurements. These versions do not have to be at the corresponding level at each information security area. For example, it's possible to use a different market version on the physical area and another market version on the system security area. Internal working revision numbers are only used by the license provider, these revisions are never used in actual analysis or measurements.

[0118] When a new major development, a new security technique has been adopted or a major shift in social behaviour within the information security areas, the market version have to shift. This is a trigger in the method to develop a new major version. When to develop new market versions, is mainly controlled by involving new standards, guidelines or other information security information sets. A new market version must also be developed if transferring a certain security feature from a higher rating level to a lower. The whole process of developing new versions and revisions is up to the license providers ability to cover the information security market and to be up to date with the day to day information security situation.

[0119] Measurement Basic Methods

[0120] In the following is described the main tasks during the actual measurement performed towards the entity. This is a principle overview. Detailed information about what and who is set in method software program depending on the level selected.

[0121] Document Analysis

[0122] Document analysis are performed by the rating reviewer team. The reviewer uses material produced by the license provider to perform the analysis. To analyse the documentation the reviewer uses the statements within the method. Demands on context and text are derived from the information set used at the measured level, i.e. rating 1 to 5. Document analysis are performed within each information security area. The grades set upon the analysis are derived from the following:

[0123] Are the appropriate (set by the method) documentation supplied by the entity

[0124] Does the context of the documentation comply with level demands

[0125] Does the text within the documentation comply within the level demands

[0126] Interviews

[0127] All interviews are performed by the rating reviewer team. This is done by asking the respondent the set of questions applicable for his or hers position weight. The material used is applicable for the measured level. Interviews can be performed by a sole reviewer team member. Interviews are performed within each information security area. The grades upon interviews is always set according to:

[0128] The respondents ability to answer in general

[0129] The respondents knowledge about the checkpoint measured.

[0130] Inspections

[0131] All inspections are performed by the rating reviewer team. Inspections mainly concern facilities in the context of information security. A checklist is used for the measured level. Inspections can be performed by a sole reviewer team member. Inspections are only performed within the physical information security area. The grades upon inspections are set upon:

[0132] Are the protections applied

[0133] The protections quality

[0134] IT-System Analysis

[0135] The IT-System analysis is performed using a software toolbox according to the actual situation of Entity IT-systems. Different modules are used in the toolbox depending on what systems are in use and also the level chosen.

[0136] Differences of Methods Depending on Level

[0137] There is also a difference to the extension of the measurements depending on which rating level that is measured. This can be seen in table 2a.

[0138] The extension of method used during the measurement is determined by which rating level that is used. Interviews will be used more extensively and they will be more comprehensive the higher the measurement level is. Documentation analysis will also be conducted more thoroughly the higher the measurement level is. Inspections will also follow this pattern. System analysis will be performed in somewhat other manner. The higher the measurement level, the amount of system checks will be extended.

[0139] Generating Method Results

[0140] To generate the actual results from the checkpoint grades the method states that several mathematical calculations will be performed. These calculations will use all the prior discussed methodology and factor like weights and templates. All different types of calculated results will be covered in this chapter.

[0141] Result Definitions and Abbreviations

[0142] Grades

[0143] CpG=Checkpoint Grade

[0144] CpWG=Checkpoint Weighted Grade

[0145] Weights

[0146] CpW=Checkpoint Weight

[0147] CaW=Category Weight

[0148] EfW=Effort Weight

[0149] Primary Results

[0150] CpR=Checkpoint Result

[0151] CpWR=Checkpoint Weighted Result

[0152] ArWR=Area Weighted Result

[0153] Secondary Results

[0154] CaR=Category Result

[0155] CaWR=Category Weighted Result

[0156] ArR=Area Result

[0157] ToR=Total Result

[0158] ToWR=Total Weighted Result

[0159] Gaps

[0160] SeG=Security Gap

[0161] PrG=Priority Gap

[0162] The Result Generating Principle

[0163] The primary results are the results used for evaluation for level fulfilment and the basis for official statement. The primary results are the CpR and the CpWR and ArWR. All other results are secondary results and are used as guides or key values in the evaluation of the results.

[0164] The primary result generating formula takes each CpR to the weighted CpWr by using the weights and transforms this to the ArWR. The level fulfilment is then based upon that ArWR is passed for all three areas; Logical, Physical and System.

[0165] Generating Method Results

[0166] The Non Weighted Checkpoint Result (Primary)

[0167] The non weighted checkpoint result (CpR) is the raw result set by the reviewer team. There are no weights used on this result and therefore the value of the result has no properties connecting it to the entity template or to the actual respondent type. This result represent if all checkpoints where equally important and if all respondents has the same information security responsibility.

[0168] The Weighted Checkpoint Result (Primary)

[0169] This result is calculated by consider different factors defined previously to affect the importance of the checkpoint. The checkpoint results are calculated based on the entity template. The weighted checkpoint result (CpWR) is the basis for the calculation of the total performance of the analysis and subsequently the results which the rating is based upon.

[0170] The Category Results (Secondary)

[0171] Category results are contraction of the results of the checkpoints that are within that category and represents a mean value. The result of a category is merely a result to seen stand alone as it is not a calculated part of the total result. The category results can be of two types:

[0172] Non Weighted Category Results (Secondary)

[0173] The raw (unweighted) category result (CaR) is generated by mean value of the non weighted Checkpoint result (CpR). These results has no correspondence to the entity template or respondent types.

[0174] Weighted Category Results (Secondary)

[0175] The weighted category result (CaWR) is based on the mean value of the weighted checkpoint results (CpWR). Thus the CpWR follows the entity template and the actual types of the respondents.

[0176] The Area Results

[0177] The area result is a contraction of the checkpoint belonging to an area and represents a mean value. An area result is a stand alone result and can be of two types.

[0178] The Non Weighted Area Result (Secondary)

[0179] The raw (unweighted) area result (ArR) is generated by all non weighted results of the checkpoints belonging to the area in question and are a mean value. These results has no correspondence to the entity template or respondents types.

[0180] The Weighted Area Result (Primary)

[0181] The weighted area result is generated by all weighted results of the checkpoints belonging to the area in question and are a mean value.

[0182] The weighted Area result (ArWR) is based on the weighted calculated results and are by that based on the entity template and the actual types of the respondents.

[0183] The Level Fulfilment (Primary)

[0184] The total result is if each of the three areas have passed a value of three. The total result is presented as “Passed” or “Failed” the rating on the actual level depending on that all areas shall have performed with grade three or higher on each the weighted area result (ArWR). To have passed no checkpoints with a high checkpoint weight shall have a result that is less than 1.

[0185] Additional information can be obtained by looking at a total result generated by the total mean values of all the checkpoint results. These additional total results can be of two types:

[0186] Non Weighted Total Result (Secondary)

[0187] Also here a raw (non weighted) total result (ToR) can be calculated based on all non weighted checkpoint results. These results has no correspondence to the entity template or the respondents types.

[0188] Weighted Total Result (Secondary)

[0189] The weighted total result (ToWR) is also calculated based on all weighted checkpoint results. This result is based upon the entity template. These results are corresponding to the entity template and the respondents types.

[0190] Gaps

[0191] The gaps are results that are distances between values set in the method and results generated by the analysis. Definitions of gaps can also be seen in FIG. 4b.

[0192] Security Gap

[0193] The security gap (SeG) is calculated for each checkpoint by comparing the checkpoint result to the norm value of three that equals the result needed to pass the demands on the checkpoint. The checkpoint result is subtracted by 3 and if the result is negative is there a security gap equal to that figure.

[0194] Priority Gap

[0195] The priority gap (PrG) is calculated by taking all checkpoint results that have a security gap and adding the security gap for the checkpoint and the difference between the actual effort weight for the checkpoint and the maximum value of five.

Method Processing

[0196] In the following will be described how to work with and implement the method. The method processing is how the results are gathered. As the method is software supported by a method software program, this is also described under this heading as well as the software toolbox for system security testing.

[0197] General Work Flow

[0198] The measurement follows a number of process steps/phases as can generally be seen in FIG. 3.a. This can also be described more in depth by a phase description. It is important to again point out that as the basis for the result is the actual performance that the Entity shows for each checkpoint, and the major part of the work is carried through by gathering and determine the performance of each checkpoint included in template.

[0199] Phase 1—Pre Study, Setting the Level Template

[0200] This phase is to determine what actual level that is preferred by the Client and requirements that the client may have. It is also to determine minor adjustments of the method, such as terminology. Further it will state what kind of documentation that is expected from the client as well as how organisation and system layout will set the parameters for interviews and system check modules. A list of Actions will be set for the Entity to fulfil.

[0201] Phase 2—Set Up of the Method Software Program

[0202] The Reviewer receives the method software program and the software toolbox. The method software program will be set with parameters for basic terminology of the Entity and data for interviews as well as system check modules.

[0203] Phase 3—Documentation Analysis

[0204] The Reviewer following the guide in the software program sets the actual measurement and results on the Checkpoints considering documentation and the results (0-5) for each Checkpoint are put in.

[0205] Phase 4—Interview Analysis

[0206] The Reviewer performs the interviews of different personnel within the entity and the results (0-5) for each Checkpoint are put into the software program.

[0207] Phase 5—Physical Inspections

[0208] Physical inspections are conducted at the premises of the Entity and results (0-5) for each Checkpoint are put into the software program.

[0209] Phase 6—System Analysis

[0210] The modules for systems tests in the software toolbox are conducted and the results (0-5) for each Checkpoint are set in the method software program.

[0211] Phase 7—Result Calculation

[0212] The result file is sent to license provider for calculation of the results according to the set up determined in the pre study phase.

[0213] Phase 8—Result

[0214] The final result is sent to the Reviewer in electronic format.

[0215] Phase 9—Report

[0216] The reviewer chooses standard report that will suit the Client directly from the software program.

[0217] Phase 10—Presentation

[0218] The reviewer will present the results to the Client. The client will also get the electronic copy.

[0219] Phase 11—Analysing the Result

[0220] The Client may reconstruct the result in a fashion that suits him and can from the electronic copy sort the result in many different ways to be able to set priorities for enhanced information security.

[0221] The process above and in FIG. 3.b is simplified somewhat and does not cover how the methods differs between different levels and/or areas.

[0222] Phase 12—Renewal of Verification

[0223] The process is a single loop process but as time will affect the security level should a renewal of the verification be necessary in order to keep the verified level, see the last step. If so the first step “Pre-study” can be much more limited and only cover differences. However if the renewal of the verification is done on a higher level a full pre-study must be carried through.

[0224] Method Software Program

[0225] The software program supports the method and contains necessary data to perform the measurement. It also serves as the basis for how to handle data between License Provider and Reviewer. The method software program generally support all phases described above.

[0226] Data Handling Between Reviewer and Licence Provider

[0227] The License Provider will send the method software program to an approved Reviewer when a Client has been contacted. The Reviewer will receive the first part contain all necessary software to be able to carry out the Pre-Study phase.

[0228] When the Pre-study Phase is done a file will be sent by the Reviewer to the Licence Provider generating the set up for the Client.

[0229] The method software program for the specific client will be sent to the Reviewer, that will put in all the results gathered and when finished a file will be sent to the Licence provider. The file will be the base for calculating the final result and these will than be sent to the Reviewer to present this to Client as the last pieces in the method software program.

[0230] It is important to point out that the License Provider will always have the mathematical criteria's for determine the final result and thus ensure that the result is done correctly.

[0231] Method Support

[0232] The method software program will contain all questions and guides of how to perform the data gathering and setting the raw results. It will also contain features that will speed up the process of gathering the data.

[0233] The method support software program contains also the values for effort weights for each checkpoint.

[0234] Result Presentation and Analysing the Result

[0235] The method software program will generate a number of standard reports to choose from. This will include both written and graphical presentations.

[0236] The report will be in a form of a database and also enable the Client and/or Entity to revise the result in a way that suits further work and actions to improve the information security.

[0237] Software Toolbox—IT-System Security Analysis

[0238] The idea with using a software toolbox is that IT-systems are somewhat insecure because the rapid development of hacker and cracker tools on the Internet.

[0239] The software toolbox contains a major part of hacker and cracker tools and other system analysis tools and it will enable modifications to adapt to be used for the actual analysis. The toolbox is built in a modular system to be adaptive to actual system. Here the variation could vary greatly when it comes to applications. In order to handle that situation are the applications dived into standard application and extended application. The standard applications are the ones that are known and which information about threats etc is available to anybody. Extended application could be unique, new or old application where information is not available. These have to be dealt with depending on what functions they may have. If they are considered to be of importance from a security point of view they will be tested and moved to as a standard application for the next test.

Method Result Presentation

[0240] In the following will be described how to interpret the results. The results are presented in two media. One media is written report and the other media is a software. The results are presented as text and also in graphical format.

[0241] Presentation of the Total Result

[0242] The presentation of the total result is presented in written form as “Passed” or “Failed” on the level measured. If passed the Entity Owner will receive an Certificate stating that the Entity measured has for example passed the Veriscan 3 (Or applicable level). Additional comments on major issues are addressed. As the total results is based on the results of each area is the total result also presented in a graphical form including the three areas, see FIG. 4a.

[0243] Presentation of Category Results

[0244] The category results are presented in a graphical format showing the weighted and non weighted results for each category within an area for all three areas. Written major comments are added.

[0245] Presentation of Checkpoint Results

[0246] For each area and under each category are the checkpoint results listed as verbal comments and connected to these are also the graphical presentation. For each checkpoint result is also the effort weight presented, see FIG. 4b.

[0247] In the graphical presentation can also the Security Gap (SeG) clearly be seen and also the Priority Gap (PrG).

[0248] Evaluation of Results

[0249] In the following will described how to interpret the various results and how to use them separately and to use them together.

[0250] General Principle

[0251] The methodology is based on the principle of that the total security level is depending on that the three sub areas has an equally sufficient security level. Within each area is then the result generated by mathematical formulas adding up the results from each checkpoint within the area. For each category is also the results mathematically calculated from the results from each checkpoint as well as there is also a total result generated by calculating all checkpoints but this is additional information.

[0252] Thus is can be stated that the method's results are gained from measuring the smallest part, the checkpoint, and summarise these into the areas. If all areas have passed a critical value is the level approved and the organisation has passed the test on the decided and measured level and can be given its certificate/Rating for that level.

[0253] As all results are numerical from total rating to area, category and checkpoint they are comparable within the level. As they are in numerical form they are possible to compare between different analysis conducted, if consideration are taken into versions and that comparison is made on the same type of value (weighted or non weighted).

[0254] Evaluate the Result on the Total Level

[0255] The result of the level measured requires that all three areas has a result of three or higher to be approved on the level. If approved the entity will be rated according to the level measured, Veriscan 1 to 5.

[0256] As the lower level are a sub set of the above level it may be possible to receive a lower rating than on the actual level measured, e.g. if not approved on measured level Veriscan 3 but approved on level 2 the organisation will be rated 2. But it is not possible to have a higher rating than the level that was measured due to that higher levels contains more extended demands and more checkpoints, e.g. if measured on level three and approved with a high margin it is still not possible to receive a higher Rating than Veriscan 3.

[0257] If a result of less that 1 is achieved on particular important checkpoints this will be stated. This may be a checkpoint necessary to have a passed result.

[0258] Taking the Secondary Total Analysis results both in weighted and non weighted form will indicate the following:

[0259] If a ToWR is higher than or in the region of 3 but the analysis is not passed, there is minor achievement needed to pass on the level and subsequently if the ToWR is lower there is major amendments necessary.

[0260] If the ToR is higher than the ToWR this shows that the entity is not good at important checkpoints. If the ToR is lower than ToWR is the organisation generally performs better on important checkpoints. This information is suitable for top management presentation and comments.

[0261] Evaluate the Result of an Area

[0262] The result of each area is on an analogue scale of 0-5, and that the result of 3 or higher for each area means that the area has been approved according to the criteria set for the level. As the method is based upon that the security demands on each area are balanced within a level, it can easily be evaluated which are needs attention if a non-approved result is achieved.

[0263] Further more the results of each area can easily be distributed to responsible managers within the entity is so preferred by the client.

[0264] For example: Logical Security Result: 2,3 Physical Security Result: 3,6 System Security Result: 2,9

[0265] The conclusion is that the Management has to look into the Logical Security Area, as the most action needs to be taken there. The System Security Area needs just some minor action to pass and the Physical Area does not need any further investments at the moment.

[0266] Within an Area the results on each checkpoint could also be evaluated. However this should be done in two different ways. First the comparison between if the performance have been generally good or poor on important checkpoints. This should be done by comparing the non weighted and weighted results on the Checkpoints of the Area, e.g. comparing Area Result without Category weight (AeR) and Area result with checkpoint weight (AeRW).

[0267] If the weighted Area result (AeWR) is lower than the non weighted area result (AeWR), the entity has mainly poor results on particular checkpoints that are more important than others, i.e. have a higher checkpoint weight. If the (AeWR), is higher than the (AeR), the organisation has reached good results in checkpoints that are generally more important then others. The second evaluation is of course to see what checkpoints that have a non-approved result and also to see what is the performance on the most important ones.

[0268] Evaluate the Result of a Category

[0269] The results of a Category is also on a analogue scale of 0-5, and that the result of 3 or higher for each area means that the area has been approved according to the criteria set for the level.

[0270] A result of X means that the specific Category has not been measured.

[0271] Evaluation should be made taking the results of categories within an area and compare weighted and non weighted results. This is additional information and could serve as a guide for management on a not to detailed level.

[0272] This is done by comparing the weighted result (CaWR) and compare it to the non weighted result of the same category (CaR). If the weighted result (CaWR) is higher than the non weighted one (CaR) is the organisation better on important categories.

[0273] Particular attention should be taken to Categories not measured.

[0274] Evaluate the Result of a Checkpoint

[0275] The results of a checkpoint is also on a analogue scale of 0-5, and that the result of 3 or higher for each area means that the area has been approved according to the criteria set for the level.

[0276] A result of X means that the specific Checkpoint has not been measured.

[0277] As the Checkpoint results are the basis both for the results but also for the actions can the evaluation of this bee done in many ways. When evaluating the Checkpoint is it also possible to use the Effort weights and also the Position weights to get more information of taking the proper actions for enhanced information security. However these results may not bee necessary to view for top management but can be used for the personnel directly responsible within the Entity for certain information security areas and categories.

[0278] The first evaluation should be done so that the security gap is considered, meaning that checkpoints with a low result should be looked into. These should then be divided into different groups. The first group is the ones with low Effort weight, which means that actions can be taken directly to correct them.

[0279] Secondly are the ones with higher effort weights where work should be initiated and evaluation of proper actions should start. Third is the group that has medium effort weights, which should be looked into individually.

[0280] Naturally the checkpoint results could be sorted within Areas and/or Categories if so preferred.

[0281] It is also important to point out that as the effort weights are general there are variations depending on the Entity resources. For example if the entity has a large IT department the costs may be lower to make correction as less eternal purchase of Consultants may be necessary.

[0282] Further Position weights could be analysed to evaluate where necessary training of information security is needed, e.g. if generally personnel with high weight have poor results but not personnel with lower, management and IT personnel needs more training than the standard users.

[0283] Particular attention should be taken to checkpoints not measured.

BRIEF DESCRIPTION OF THE FIGURES

[0284] FIG 1 a Shows entities with described needed measured information security level. Two entities shares or exchange information that is considered valuable. The entity to the left has a certificate on Veriscan level 3 but does not know what information security level the right Entity has. Insecurity arises and the transaction may not take place. If however the right entity also had a corporate certificate on a Veriscan level suitable to them, the left entity can evaluate if they can handle the information properly. The corporate certificate has enable trust and the transaction may take place. Comparison between entities has been enabled when it comes to such a complex area as information security by simply stating a figure created related to a norm.

[0285]FIG. 2a FIG. 2a shows the principle of the breakdown of terms within an area.

[0286] Table 2 b Table 2 b shows the method differences between the levels.

[0287]FIG. 3a This figure shows the method steps.

[0288]FIG. 4a FIG. 4a shows the total results in graphical form.

[0289]FIG. 4b FIG. 4b shows a graphical result table

A COMPLEMENTARY WAY OF DESCRIBING THE CONCEPT

[0290] The concept is described in a complementary way by means of 65 slides of a slide show enclosed on separate pages numbered 1-33.

[0291] The method according to the invention could also be extended to operational risk rating.

[0292] Operational Risk is here defined as an organisation total risk of loosing immaterial assets.

[0293] As information is a major part of immaterial assets is it possible to add a fourth area to the three areas for information security to control and rate also Operational Risk. This Fourth area is subsequently only added if Operational Risk Rating is selected rather than Information Security Rating.

[0294] This is called Veriscan Rating of Operational Security.

Definition Organisational Security

[0295] Operational risks is defined as other risks of errors, mistakes crime or accidents that causes directly or indirectly losses.

[0296] Organisational Security risks are defined as risks as above caused by the organisations structure and functions and environment. Environment could be linked both to factors that the organisation controls as well as the environment in which the organisation operates that is outside of the organisation's control.

Terminology and Method Definitions

[0297] The method is the same as for measuring Information Security.

[0298] The categories and checkpoints are of course of a different type. Categories are such as: Legal, Image and PR, Control Systems, Business Strategies, Authorities, Financial, Market Mix, Spirit, Product & Service Structure.

Measurement of Organisational Risk

[0299] The measurement is basically the same as for the other areas and only abbreviations will be presented in these chapter.

[0300] Measurement Basic Methods

[0301] The measurement are using the same methods as for the another three areas with one slightly different aspect and that is that the measurement of IT/Systems is naturally not used.

[0302] For measuring Financial Risk, may also sector or other methods be used, as these are from the beginning in mathematical form that can be transferred to the relative system in this method.

[0303] Area Results

[0304] The area result is presented separately, and also in a graphical form including the other three areas.

[0305] Level Fulfilment

[0306] To add organizational Risk to the other thee areas states that the measurement of fulfillment is done for Operational Security and not for information security. But as information security is part of the Operational Security must all areas have been measured and have passed result to be rated for Operational Security. This is the identical principal as Informational Security Rating but there are four areas to consider.

Method Processing

[0307] The method processing for Operational Risk Measurement is done in addition to the information security measurement and follows it's workflow. Only differences will be stated in this chapter.

[0308] The major difference is that from start it must be clear if it is the information security that should be measured with Logical, Physical and System areas or operational Security which ads the fourth area Organisational Risk.

[0309] The workflow is in principle the same with the exception of that System analyses is not conducted.

[0310] There will be additions to all other phases to cover the forth area. Generally the fourth area means that each phase is spitted up with two focuses. One is the same to cover Information Security and the second focus is the Organisation Security measurement. The pre-study for example will be extended as a much more documentation and more people have to interview and this must be set from start.

Method Result Presentation

[0311] The result is presented in the same manor but with the addition of the fourth area. Please see below. The symbol for passed rating for Operational Security is different as for information security Rating and the name are also different in order to not misjudge the different measurements. 

1. Graphical tool for decision making especially for setting priorities comprising at least one diagram (1) having a first scale (2) which reaches in a first direction along a first axis (3), at least a first (4) and a second (5) potential action fields the identified value of which (4 a, 4 b) is graphically represented on said first scale (2) in said diagram (1) whereby a second scale (6) is arranged along said first axis, characterised in that said second scale (6) reaches in an opposite direction to said first scale. 